Multipath delivery for adaptive streaming

ABSTRACT

A method for delivering content via adaptive streaming technique over multiple communication paths and a device implementing the method are disclosed. 
     The method for providing a content to be rendered at a client device comprises at least a first past being identified by the address of a first interface and the address of a first server interface, and a second path being identified by the address of a second interface and and the address of a second server interface, the content being available under at least two versions having an encoding quality corresponding to a supported bit rate constraint, each of the at least two versions being temporally split into chunks corresponding to an identical rendered duration of the content, a chunk being identified by a time index i and by one of the supported bit rate. 
     According to the invention the method comprises the steps of:
         measuring a first available bit rate on the first path and a second available bit rate on the second path;   determining a requested bit rate among the supported bit rate from the measured first available bit rate and from the measured second available bit rate;   sending a first request via the first path for receiving a first part of the chunk identified by the time index i and by the requested bit rate and a second request via the second path for receiving a second part of said chunk, said of the chunk being complementary; and each of said parts of the chunk having a size being computed from the determined available bit rate;   receiving the requested first part via the first path and the requested second part via the second path.

FIELD OF THE INVENTION

The present invention relates generally to adaptive streaming and in particular to a method for delivering content via adaptive streaming technique over multiple communication paths and a device implementing the method.

BACKGROUND OF THE INVENTION

This section is intended to introduce the reader to various aspects of art, which may be related to various aspects of the present invention that are described and/or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present invention. Accordingly, it should be understood that these statements are to be read in this light, and not as admissions of prior art.

Media delivery streaming solutions are mainly based on protocols such as Real time streaming Protocol (RTSP) as defined in the IETF RFC 2326, Microsoft Media Server (MMS) proprietary protocol from Microsoft or Real Time Messaging Protocol (RTMP) proprietary protocol from Adobe Systems.

More recently a streaming technique, said adaptive and based on HTTP protocol, has emerged with different flavors such as the “Move Adaptive Stream” from Move Networks, the “HTTP Live Streaming” from Apple Inc. and the “IIS (Internet Information Services) Smooth Streaming” from Microsoft. The benefit of using the HTTP protocol in these streaming solutions is its capability to cross over NAT and firewall seamlessly. The HTTP adaptive streaming technology provides a way to compensate erratic network behavior regarding available bandwidth by continuously and gracefully upgrading or downgrading the video quality in order to fit with the bandwidth constraint.

In more details, WO 2005/109224 A2 from Move Networks describes a mechanism in an Agent Controller Module hosted in the client side and able to adapt to the fluctuant network bandwidth thanks to the fact that the media to stream is previously organized in a plurality of streamlets, also called chunks, each of them being encoded from low to high bitrates. According to the available network bandwidth and some other additional information a monitoring tool incorporated in the Agent Controller Module uses the HTTP protocol to request the server to send the best suited chunk to be streamed over a TCP/IP connection. On an elementary chunk basis the quality is up-shifted or down-shifted according to the Agent Controller Module.

WO 2009/020552 A1 from Move Networks discloses a system in which a client carries out a “parallel retrieval” method of more than one streamlet or part or streamlet at one time using multiple connections between the client and a single server.

The IIS Smooth Streaming Technical Overview, from Alex Zambelli, Microsoft Corporation, March 2009, describes the IIS Smooth Streaming Technique based on HTTP protocol over TCP/IP connection. The media to be streamed by the Server is previously chopped into chunks representing for example one to ten seconds duration. Then these chunks are encoded according to the H.264/MPEG-4 AVC standard at different bitrates and stored within a MP4 file format container. The mechanism selecting the bit rate according to the network bandwidth fluctuation and requesting seamlessly the corresponding chunks to the server is entirely implemented in the client side through an application code, the Silverlight application. The HTTP Live Streaming supports dynamic switching between streams of different data rates in response to changing connection speeds.

Apple Inc. submitted an Internet Draft to IETF in October 2009 on an HTTP streaming method specification entitled “HTTP Live Streaming draft-pantos-http-live-streaming-02”. The HTTP streaming architecture is based on 3 pillars: a Server, a Distribution, through a Web server or a Web caching system, and a Client. The media to be streamed is a video encoded in H.264 and an audio encoded in AAC. At a server, it is encapsulated in MPEG-TS containers and fragmented into chunks of equal duration with a specific tool named Apple stream segmenter. This tool generates the chunks that are saved into *.ts files and an index file *;m3u8 constituting the chunks playlist. Then a client fetches the index file first thanks to an URL pointer. The index file in turn specifies the location of the available media files, decryption keys, and any alternate streams available. For the selected stream, the client downloads each available media file in sequence.

HTTP adaptive streaming methods are generally oriented on adapting media viewing experience of the end user according to network congestion. Indeed, as soon as the network bandwidth measured by the client device decreases, the latter requests chunks which are less restrictive with respect to network bandwidth requirement; the “low bandwidth chunks”. Conversely when the congestion problems decrease, the client device requests chunks which are more restrictive with respect to network bandwidth requirement; the “high bandwidth chunks”.

The FIG. 1 a illustrates the main steps of adaptive streaming method according to prior art. FIG. 1 a shows a video content has been (pre-) encoded into four versions (version A, version B, Version C and version D) with increasing supported bit rates implying progressive quality increase. The encoded video content is split into chunks that allow seamless switching from one bit rate to another. All the video chunks correspond to an identical fixed duration. These chunks are more or less big: thus requiring higher/lower bandwidth and providing better/lesser video quality, depending on the supported bit rates. All the versions of the content stored in the server CS1 (version A, version B, Version C and version D) are split into a fixed number of chunks, 14 chunks in the FIG. 1 a.

On FIG. 1 a, a first step of the method according to prior art is shown: a client device CD monitors the bit rate BR1 of a path P1 connecting the client device CD to the server CS1.

In a second step, the client device CD determines a requested bit rate RBR compliant with the measured bit rate BR1. For example the requested bit rate RBR is the largest of supported bit rates BRA, BRB, BRC, BRD which is also less than or equal to the measured bit rate BR1.

In a third step, the client device requests via the path P1 a chunk identified by a time index i (here 1<i<14) and the requested bit rate RBR.

In a fourth step, the client device CD receives still from the path P1 said chunk i at the requested bit rate RBR from the server CS1.

The four steps are repeated each time a chunk is needed.

The FIG. 1 b shows a temporal evolution of the bit rate for a method of adaptive streaming of the prior art as presented above.

The curve on FIG. 1 b shows the monitored bit rate BR1. Below the curve, one represents the chunk which is downloaded from the server. A typical adaptive client will continuously monitor the available bitrate (or bandwidth) and select the requested bit rate which is less than or equal to the available bit rate BR1 for the next chunks to be retrieved. Of course, depending on the implementation and the environment (network technology, application) the strategy may be conservative—i.e. the client requests higher bit rate chunk only after a certain time ensuring smooth upgrade transition; the client requests lower bit rate chunk as soon as it detects a bandwidth decrease implying rapid downgrade transition)—or more aggressive. In FIG. 1 b, there are 4 different bit rates depicted corresponding to the four version of the encoded content.

With the adaptive streaming solutions explained above, the video stream that is acquired by the client CD chunk after chunk does not have a consistent quality with time. It is understood that the user experience may be damaged when the bandwidth goes down. The video never or rarely interrupts but the quality could be very poor. There is no other particular solution to preclude this situation than reducing the quality of transferred content. Increasing the receiver buffer will avoid the dry effect wherein a chunk delivery takes more time than expected but will not do anything against temporary low bandwidth availability.

One of the goals of the present invention is to fight the temporary lack of bandwidth (or bit rate quick slowdown) by using at least two (independent) delivery paths both being controlled by the client. These delivery paths must present transmission characteristics as much orthogonal as possible. This can be achieved having one client (e.g. a terminal) connected to a server via at least two different access networks (e.g. broadband xDSL and cellular 3G/LTE) or/and connected to a server connected to at least two similar access networks (possibly managed by two different internet service providers) or this can be realized by having one client connected to at least, two servers, each server being connected to a different access network. The latter may be easier to implement and we will focus on this implementation for the invention. In the rest of the document a server can be viewed as a physical box connected to a dedicated link/path or as a logical entity connected through a dedicated path/link as well.

It is understood that the invention applies with at least two links/paths. In case of one machine hosting logical servers, the machine must support multi homing (i.e. can be connected to more than one network interface, each having a dedicated—e.g. IP—network address).

Instead of having the chunk files stored on one server, they are stored on two servers accessible through two different communication paths (each server has its own network accesses and its own IP address).

When the client detects that the available bit rate is slowing down on one of the paths, it can download the next chunk, or the next part of the chunk, from the alternative server. This can be implemented through a failover algorithm (use one main path and use the alternative path when the main path is struggling), through a load sharing algorithm (use both paths concurrently: a chunk is delivered partly from one of the server and partly from the other server or even through a bandwidth limited algorithm (guarantying a minimum global bit rate, by a main path P1 and additional paths P2, P3 in case an additional bit rate is needed to fulfill the global bit rate objective).

SUMMARY OF THE INVENTION

The technical problem that the present invention intends to solve is to improve an adaptive streaming method for render it less sensitive to problems of caused by temporary low bandwidth availability over a communication path.

Thus, the present invention concerns according to a first aspect, a method for for providing a content to be rendered at a client device CD comprising at least a first and a second communication interface CI1, CI2, wherein said first and second communication interface CI1, CI2 having a communication address, said content being accessible to the client device CD via at least a first and a second server communication interface SI1, SI2 having a communication address, a first path P1 being identified by the communication address of said first communication interface CI1 and the address of the first server communication interface SI1, a second path P2 being identified by the communication address of said second communication interface CI2 and the address of the second server communication interface SI2, said content being available under at least two versions having an encoding quality corresponding to a supported bit rate BRA, BRB constraint, each of said at least two versions being temporally split into chunks corresponding to an identical rendered duration of the content, a chunk being identified by a time index i and by one of the supported bit rate BRA, BRB, said content being simultaneously accessible by said client device CD though said first and a second path P1, P2. According to the invention the method comprises, at the client device CD, steps of:

S1 measuring a first available bit rate BR1 on the first path P1 and a second available bit rate BR2 on the second path P2;

S2 determining a requested bit rate RBR among the supported bit rate BRA, BRB from the measured first available bit rate BR1 and from the measured second available bit rate BR2;

S3 sending a first request via the first path P1 for receiving a first part of the chunk identified by the time index i and by the requested bit rate RBR and a second request via the second path P2 for receiving a second part of said chunk, said first and second part of the chunk being complementary;

S4 receiving the requested first part via the first path P1 and the requested second part via the second path P2.

Thus, the present invention concerns according to a second aspect, a client device CD for receiving a content to be rendered, said client device CD comprising at least a first and a second communication interface 11, 12, wherein said first and second communication interface CI1, CI2 having a communication address, said content being accessible to the client device CD via at least a first and a second server communication interface SI1, SI2 having a communication address, a first path P1 being identified by the communication address of said first communication interface CI1 and the address of the first server communication interface SI1, a second path P2 being identified by the communication address of said second communication interface CI2 and the address of the second server communication interface SI2, said content being available under at least two versions having an encoding quality corresponding to a supported bit rate BRA, BRB constraint, each of said at least two versions being temporally split into chunks corresponding to an identical duration of the content, a chunk being identified by a time index i and by the supported bit rate BRA, BRB, said content being simultaneously accessible by said client device CD though said first and a second path P1, P2.

According to the invention the client device CD comprises:

Means for measuring a first available bit rate BR1 on the first path P1 and a second available bit rate BR2 on the second path P2;

Means for determining a requested bit rate RBR among the supported bit rate BRA, BRB from the measured first available bit rate BR1 and the measured second available bit rate BR2;

Means for sending a first request via the first path P1 for receiving a first part of the chunk identified by the time index i and the requested bit rate RBR and a second request via the second path P2 for receiving a second part of said chunk, said first and second part of the chunk being complementary;

Means for receiving the requested first part via the first path P1 and the requested second part via the second path P2.

The invention proposes an enhancement of the adaptive streaming methods of the prior art based on the usage of more than one server either in switched way or in a concurrent way allowing:

a better overall quality

an improved service robustness from the client's perspective;

an improved service scalability from the server's perspective in case the chunks are encoded according to SVC.

Another advantage of the invention resides in its compatibility with architectures of known streaming devices. A method according to the invention can be implemented between a server and a client according to prior art without any modification for the player receiving the stream to be played back.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will be better understood and illustrated by means of the following embodiments and execution examples, in no way limitative, with reference to the appended figures on which:

FIG. 1 a, shows a client device CD requesting a content to a server using an adaptive streaming method according the prior art, already described above;

FIG. 1 b, shows a temporal evolution of bit rate corresponding to an adaptive streaming method according the prior art, in regard with an evaluated bit rate, already described above;

FIG. 2, shows an implementation of a multi paths adaptive streaming method according to the embodiment;

FIG. 3 a is a block diagram of a client device according to the embodiment;

FIG. 3 b, shows a temporal evolution of measured available bit rate for an adaptive streaming method according to the embodiment thus using a concurrent approach,

FIG. 4 a, shows a temporal evolution of bit rate for an adaptive streaming method according the embodiment.

FIG. 4 b, shows a temporal evolution of bit rate for an adaptive streaming method according the embodiment thus using a failover approach.

In FIG. 3 b, the represented blocks are purely functional entities, which do not necessarily correspond to physically separate entities. Namely, they could be developed in the form of hardware or software, or be implemented in one or several integrated circuits.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

It is to be understood that the figures and descriptions of the present invention have been simplified to illustrate elements that are relevant for a clear understanding of the present invention, while eliminating, for purposes of clarity, many other elements found in typical digital multimedia content delivery methods and systems. However, because such elements are well known in the art, a detailed discussion of such elements is not provided herein. The disclosure herein is directed to all such variations and modifications known to those skilled in the art.

A multi paths adaptive streaming method for delivering a content to a client device CD according the embodiment is described in this section and illustrated with FIG. 2.

The client device according to the embodiment is represented in FIG. 2. The client device CD is accesses to a content through a first and a second path P1, P2. The first path P1 is defined by a communication address of a first communication interface CI1 of the client device CD and a communication address of a first server communication interface SI1. Accordingly the second path P2 is defined by a communication address of a second communication interface CI2 of the client device CD and a communication address of a second server communication interface SI1.

Advantageously, a single server CS1 comprises the first and second communication interface CI1, CI2.

Advantageously, the first and second communication interface CI1, CI2 are comprised in two different servers CS1, CS2. This situation will be illustrated in FIG. 2.

Advantageously, the servers CS1, CS2 are HTTP servers.

The client is also connected to a player 4 (not represented). On the server side, chunks are streamed upon the client request, using HTTP protocol over TCP/IP connection. The client requests parts of chunks according to an algorithm described hereinafter and based on path bit rate measurements. A chunk should have been fully received by the client before it is decoded and rendered. The client device CD is able to request content simultaneously through a first and a second communication interface CI1, CI2.

It is understood that the content can be downloaded through said paths P1, P2. In the following one will depict a situation where said content is duplicated on different servers CS1, CS2: in other word the two server communication interfaces SI1, SI2 are located on two different servers CS1, CS2. The situation is similar if server communication interfaces SI1, SI2 are located on a single server CS1 where the content is stored: the only difference is the content is not duplicated on two different servers. This contributes to security by supplying a data redundancy.

The content is for example a video or an audio content which is downloaded for being rendered at client side. For example once downloaded the client device CD transmits said content at a player (not represented on FIG. 2) chunk by chunk for being played back.

The content is for example generated by a content preparation tool. This tool generates compressed video and audio content (e.g. H264 and MP3 respectively) at at least two targeted (or supported) bit rate (e.g. BRA=300 kbps, BRB=600 kbps, BRC=1000 kbps, BRD=2000 kbps). The content preparation tool multiplexes them for producing a MPEG TS (Transport Stream) chunk serie per supported bit rate.

All the chunks correspond to an identical duration of the content e.g. 2 seconds for each targeted bit rate. A chunk is identified for example by a time index i (1<i<14 in the example) and by one of the supported bit rate BRA, BRB, BRC, BRD.

On all the following figures, the chunks are represented as rectangle boxes: the horizontal size of said boxes are identical and correspond to the above described identical duration. The vertical size of said rectangle boxes illustrates the quality of said chunk and corresponds to one of said supported bit rate BRA, BRB, BRC, BRD. Then, all the chunks belonging to a chunk serie has an identical vertical size. But the size of the chunks belonging to a chunk serie does not have necessarily identical sizes. The sizes of the chunks of a serie identified by different time index depend on the time evolution of content.

The chunk series are stored on both servers CS1, CS2 as represented in FIG. 2 and identified by “version A”, “version B”, “version C” and “version D”. In the chosen representation, all the chunks stored on both servers CS1, CS2 are identical except the time index i.

The two servers CS1, CS2 are connected to the client device CD over two different access networks forming two independent paths (P1, P2).

At the connection set up, a manifest file is received by the client device CD from at least one of the servers CS1, CS2. This manifest file comprises a list of the supported bit rates BRA, BRB, BRC, BRD and for each supported bit rates BRA, BRB, BRC, BRD the list further comprises the total number of chunks, and the chunk size.

Advantageously, a list of alternative servers (or alternative server communications interface addresses) is proposed in said manifest file.

The FIG. 3 a shows the four main steps of a method for providing a content to client device CD according to the embodiment.

In a first step S1, the client device CD monitors the available bit rate on the paths P1, P2: the available bit rate BR1 is measured continuously on the path P1 and the available bit rate BR2 is measured on the path P2.

Advantageously, the bit rates BR1, BR2 are measured periodically at a period lower or equal to the chunk duration: in the described example this period is 2 seconds.

Advantageously, the step S1 of measuring first and second available bit rates BR1, BR2 consists in computing a round trip time of a request sent by the client device CD through said first and second path P1, P2 and of an acknowledgment message sent by the server CS1, CS2 through said first and second path P1, P2 in response to said request.

In a second step S2, the client device CD determines a requested bit rate RBR among the supported bit rate BRA, BRB, BRC, BRD from the measure of the first and second bit rate BR1, BR2. The requested bit rate RBR is chosen exclusively among the supported bit rates BRA, BRB, BRC, BRD as defined in the manifest file. The requested bit rate RBR defines the bit rate of the requested chunk.

Advantageously, it comprises a further step of receiving by the client device CD a list of the supported bit rates BRA, BRB via at least one of the paths P1, P2 and further steps of for receiving for each supported bit rates BRA, BRB sizes of the chunks.

Advantageously, the client device CD further comprises means for receiving, via at least one of the first and second path P1, P2, information related to the supported bit rates BRA, BRB and for each supported bit rates BRA, BRB information related to the size of the chunks.

Advantageously, the step S2 of determining the requested bit rate RBR consists in selecting the largest bit rate among the supported bit rates BRA, BRB, BRC, BRD which is lower than or equal to the sum SUM of the measured first available bit rate BR1 and of the measured second available bit rate BR2 minus a provision.

Advantageously, the means for determining a requested bit rate RBR is adapted for evaluating a sum SUM of the measured first available bit rate BR1 and of the measured second available bit rate BR2 and said means is adapted for selecting the largest bit rate among the supported bit rates BRA, BRB which is lower than or equal to the sum SUM of the measured first available bit rate BR1 and of the measured second available bit rate BR2 minus a provision.

In a third step S3, the client device CD sends a request for a chunk identified by the time index i and the requested bit rate RBR to both servers CS1, CS2 via respectively paths P1 and P2. More particularly, the client device CD sends a request to the server CS1 via path P1 a first part of the chunk at the requested bit rate RBR and to the second server CS2 via path P2 a second part of the chunk, said first and second part of the chunk being complementary.

By using the term “complementary”, one wishes to describe that there is no overlap between the first part and the second part and that the aggregation of both the first and second part result in the whole chunk.

The fourth step S4 consists in receiving by the client device CD concurrently the requested first part via the first path P1 and the requested second part via the second path P2. The paths P1, P2 are used concurrently for providing the chunk.

By using the term “concurrently” one wishes to highlight that both parallel paths P1, P2 are used simultaneously for downloading a single chunk in its entirety: none part of the chunk is downloaded by both paths P1, P2.

The client device CD according to the embodiment is illustrated in FIG. 3 b. The client device CD comprises a first interface CI1 to a first network which comprises the protocol stacks for communicating with a first server communication interface of the server CS1 connected over the first network and a second interface CI2 to a second network which comprises the protocol stacks to communicate with a second server communication interface of the server CS2 connected over second network. In particular the first and second network is the Internet. Of course it could be any other type of network enabling a client to communicate to a server.

The client device CD also comprises a third interface 16 to connect to a player that is adapted to decode and render the content. Of course the third interface could enable connecting more than one player. It could be an interface to a network enabling to connect one or more players. The client device CD also comprises a processor 11 for processing the applications stored in the client. It further comprises storing means 12, such as a memory, for buffering the chunks or the parts of the chunks received from the servers before they are transmitted to the player. In particular the memory is a volatile memory. Of course the client comprises a non-volatile memory, not represented, for storing applications running on the client. The client could be implemented in a gateway device; the client device can be implemented as software or hardware.

The requested first part has a first size NB1, the requested second part comprising has a second size NB2.

Advantageously, a ratio between said first size NB1 and said second size (NB2) is equal to a ratio between the measured first available bit rate BR1 and the measured second available bit rate BR2.

Advantageously, the step S2 of determining the requested bit rate RBR comprises a step of evaluating a sum SUM of the measured first available bit rate BR1 and of the measured second available bit rate BR2 and the requested bit rate RBR is determined from the sum SUM.

Advantageously, the first size NB1 is proportional to a size of the chunk identified by the time index i and the requested bit rate RBR and a ratio between the measured first available bit rate BR1 and the sum SUM.

Of course, various implementations of the method according to the embodiment are available involving the client device CD requesting parts of chunks via parallel paths P1, P2, . . . , Pn. The client device CD opens connections to n servers CS1, CS2, . . . , CSn where a content is available under at least two versions corresponding to respectively two different supported bit rates BR1, BRB. The client device CD sends in parallel requests for non-overlapping parts of a chunk of content concurrently from these servers CS1, CS2, . . . , CSn.

A waited advantage of the method is to spread the traffic load across the available servers CS1, CS2, . . . , CSn. The load repartition is recomputed for every chunk. The load requested from each server CS1, CS2, . . . , CSn is determined by the size of the chunk part requested from this server. The client device CD indicates the number of bytes it wishes to retrieve from each server by including a byte range header. This header has the following format:

Advantageously, the request sent by the client device is a HTTP request.

GET/path/example.jpg HTTP/1.1

Host: example.com

Range: bytes=0-999

In the above example, the request means that the client device requests for the first 1000 bytes of the specified resource “example.com”. With each request/response with a server for a given range of a given chunk, the client device CD computes the current available bit rates BR1, BR2, . . . BRn as follows:

BR1i=nbytesSC1,i 8÷timeSC1,i

Where nbytesCS1,i is the number of bytes requested from server CS1 at for the chunk with time index i (also name “iteration”) and timeCS1,i is the duration required to download the requested chunk part from server CS1 for the chunk having time index i.

This instantaneous available bit rate measurement can be used to feed a smoothing algorithm that guarantees both a progressive quality improvement and a quick response to severe network degradations. The smoothing algorithm gives an available bit rate estimate that can be used to request the next chunk.

E1,i=f(BR1,i,BR1,i−1, . . . ,BR1,i−k)

In case, n servers are available, the total available bit rate for downloading the next chunk is:

${SUM} = {\sum\limits_{{s = 1},\; \ldots \;,n}E_{s,i}}$

Advantageously, it involves a further step SA not represented in FIG. 3 a for determining whether the first and second available bit rates BR1, BR2 measured over the paths P1, P2 are larger than a threshold value BRTH1, wherein the four steps S1, S2, S3, S4 are carried out exclusively for paths P1, P2 over which the client device CD determines the measured available bit rate BR1, BR2 is greater than the threshold value BRTH1.

In another embodiment, the concurrent mode of operation is performed just for reaching a target bit rate greater than or equal to a threshold BRTH2. A use case for this mode of operation would be to allow guarantying a given bit rate BRTH2 but not at any price by mobilising all the available paths. In other words, to use a second server CS2 only if it is needed for reaching the requested bit rate BRTH2.

The content is downloaded chunk by chunk to the client device CD only from the single server CS1 via the path P1. The first available bit rate BR1 on the path P1 is measured by the client device CD. The four steps S1, S2, S3, S4 are carried out exclusively when the client CD determines that the available bit rate BR1 is less than a threshold BRTH2 and in that case the step S2 of determining the requested bit rate RBR consists in selecting the largest bit rate among the supported bit rates BRA, BRB which is lower than or equal to the threshold BRTH2 minus a provision.

The requested bit rate RBR of the next chunk to download is the largest supported bit rate (among the supported bitrates BRA, BRB, BRC, BRD as defined in the manifest file) lower than or equal to the total available bit rate BR1+BR2. The chunk size (expressed in bytes) can be approximated as:

size=RBR·duration÷8

With no minimum bit rate threshold, the number of bytes to download from the s-th server for the next iteration is directly proportional to the share of the s-th measure of available bit rate BR1 from the total bandwidth SUM.

nbytes_(s,i+1)=size·E _(s,i)÷SUM

When a minimum bit rate threshold BRTH1 comes into play, one assigns a multiplicator ks to each server contribution, which allows to disable the servers whose bit rate is below the threshold. When the bit rate BRs corresponding to the path Ls between the client device CD and the server CSs is greater than or equal to the threshold then ks=1. When the bit rate BRs is lower than the threshold then ks=0. The total bit rate formula becomes:

${SUM} = {\sum\limits_{s = {{1\;...}\; n}}{k_{s} \cdot E_{s,i}}}$

which is obviously lower than the total bit rate calculated without threshold. The number of bytes to download from the s-th server becomes:

nbytes_(s,i+1)=size·k _(s) ·E _(s,i)÷SUM

These numbers of bytes are used to request the appropriate byte ranges from each server, so if there are n servers, the client requests

Range [0; nbytes1-1] from the server CS1

Range [nbytes1; nbytes2-1] from the server CS2

Range [nbytes1+nbytes2; nbytes3-1] from the server CS3

Range

$\left\lbrack {{\sum\limits_{i = {{{1\;...}\; k} - 1}}{nbytes}_{i}};} \right.$

nbytesk-1] from the server CSk (k<n)

Range

$\left\lbrack {{\sum\limits_{i = {{{1\;...}\; n} - 1}}{nbytes}_{i}};} \right.$

endoffile] from the server CSn

The last range uses a special range end indication to cope with the fact that the chunks are often of unequal size. This way, the last range allows the client to retrieve the end of the chunk without knowing its exact size.

Upon reception of the byte ranges from all the servers, the client device CD simply concatenates the byte ranges in ascending order to reconstruct the entire chunk. This chunk is then consumed by the player module normally, as if it originated from a single server.

Advantageously, the four steps S1, S2, S3, S4 are carried out each time a chunk is downloaded from the servers CS1, CS2.

The method according to the embodiment is also adapted for overcoming drastic decrease of a bit rate over one of the paths.

Advantageously, the client device CD comprises means for determining whether the available bit rate over one of the paths P1, P2, P3 is less than a threshold value BRTH2, BRTH3.

The client device CD is adapted for example for determining whether a delivery duration of said requested part of the chunk i exceeds a threshold value DTH

In consequence the client device CD may decide, during an iteration, to stop (or ignore) processing the end of an ongoing request (e.g. bytes range) and submit immediately a new request to a next server for getting the remaining bytes of the range to completed. This next server is for example the server which is reachable with highest bit rate or a group of server. In that case, the client sent a request for receiving the fragment of the part of the chunk which is not yet received.

Let's illustrate the method on an example where the content is accessible to the client device CD via three independent paths P1, P2, P3, for example these content are duplicated on three servers CS1, CS2, CS3, the requested bit rate RBR is determined form a first, a second and a third available bit rate BR1, BR2, BR3 measured respectively on the first, second and third paths P1, P2, P3. The client device CD has requested a first part of the chunk identified by time index i and the requested bit rate RBR via the first path (P1), a second part of said chunk via the second path P2, a third part of said chunk via the third path P3.

The method according to the embodiment involves further steps of:

When the requested first and second part are completely received by said client device CD, a first fragment of the third part being received by the client device CD and when the client device CD has determined that the available bit rate BR3 over the path P3 is less than a threshold value BRTH3,

S5 sending a request via the path P1 for receiving a first part of the third fragment of the third part of the chunk identified by the time index i and sending a request via the path P2 for receiving a second part of the third fragment of the third part of the chunk identified by the time index i via the path P2, said first and second part being complementary parts of said third part.

For the path P2 having a bit rate below a threshold BRTH3, the client requests a fragment of chunk (e.g. the current chunk). For example a fragment whose size is half the threshold BRTH3 multiplied by the chunk duration (e.g. 2s).

${nbytes}_{{{CS}\; 3},{i + 1}} = \frac{\left( {{BRTH}\; {3 \div 8}} \right) \cdot {duration}}{2}$

This fragment is only used to maintain an accurate bit rate evaluation for this particular path. The fragment is not passed to the player.

In a further embodiment, one adapts the algorithm to redistribute the load during the duration of a single chunk.

The temporal evolution of the measured bit rate BR1, BR2 corresponding to an embodiment evolving threshold value BRTH2 is shown on FIG. 4 a.

A first curve (plain line) shows the temporal evolution of measured bit rate BR1 on a first path P1. A second curve (dashed line) shows the evolution of measured bit rate BR2 on a second path P2. A third curve (dashed bold line) shows the evolution of measured total bit rate BR1+BR2. Here it is constant.

This is an advantage in comparison with prior art presented above: even if there are some temporal fluctuation of measured bit rate on a single path, the fluctuation are averaged when considering the aggregated bit rate here BR1+BR2. Correlatively the requested bit rate BRB is constant and then, the quality of the chunks received by the client device is constant even there are bit rate fluctuations over the paths P1, P2.

On the same figure one shows the first and second part of the chunk received by the client device CD respectively through path P1 and path P2: The horizontal striped boxes show the first parts of chunk received via the first path P1 and the plain boxes show the second parts of chunk received via the second path P2. Here the received chunks have all the same requested bit rate RBR because the aggregated bit rate here BR1+BR2 is constant. But, according to the relative fluctuation of measured bit rates BR1 and BR2 the relation between the size of the first part and the size of the second part varies temporally due to the temporal fluctuation of measured available bit rates.

Starting with similar hypothesis on temporal evolutions of the measured bit rate, FIG. 4 b shows the parts of chunks download through the first and second path P1, P2 when considering a threshold BRTH2.

The idea here is to implement a concurrent download only by specific conditions for example when the available bit rate BR1 measured on path P1 is lower than a threshold BRTH2. In normal operation, a download on a single server is implemented. This situation is shown on FIG. 4& where the client device CD requests and receives a chunk via a single path P1 only when the plain curve is lower than the threshold BRTH2.

Accordingly, as soon as the measured bit rate BR1 is lower than said threshold BRTH2, the client device measures a second available bit rate BR2 on the other path P1 and request parts of the chunk via both paths.

References disclosed in the description, the claims and the drawings may be provided independently or in any appropriate combination. Features may, where appropriate, be implemented in hardware, software, or a combination of the two.

Reference herein to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one implementation of the invention. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments necessarily mutually exclusive of other embodiments. 

1-15. (canceled)
 16. A method for providing a content to be rendered at a client device comprising at least a first and a second communication interface, wherein said at least first and second communication interface having a communication address, said content being accessible to the client device via at least a first and a second server communication interface having a communication address, a first path being identified by the communication address of said first communication interface and by the address of the first server communication interface, at least a second path being identified by the communication address of said second communication interface and by the address of the at least second server communication interface, said content being available under at least two versions having an encoding quality corresponding to a supported bit rate constraint, each of said at least two versions being temporally split into chunks corresponding to an identical rendered duration of the content, a chunk being identified by a time index i and by one of the supported bit rate, said content being simultaneously accessible by said client device though said first and a at least second path, wherein it comprises, at the client device, steps of: determining a first available bit rate on the first path and at least a second available bit rate on the at least second path; determining a requested bit rate among the supported bit rate from the determined first available bit rate and from the at least determined second available bit rate; sending a first request via the first path for receiving a first part of the chunk identified by the time index i and the determined requested bit rate and sending at least a second request via the at least second path for receiving at least a second part of said identified chunk, said parts of the chunk being complementary, each of said parts of the chunk having a size being computed from the determined available bit rate; receiving the requested first part via the first path and the at least requested second part via the at least second path.
 17. The method according to claim 16 wherein said content is simultaneously accessible by said client device though two paths, the requested first part have a first size, the requested second part have a second size, and wherein a ratio between said first size and said second size is equal to a ratio between the determined first available bit rate and the determined second available bit rate.
 18. The method according to claim 16, wherein the step of determining the requested bit rate comprises a step of evaluating a sum of the determined first available bit rate and of the at least determined second available bit rate and the requested bit rate is determined from the sum
 19. The method according to claim 18, wherein the step of determining the requested bit rate consists in selecting the largest bit rate among the supported bit rates which is lower than or equal to the sum of the determined first available bit rate and of the at least determined second available bit rate minus a provision.
 20. The method according to claim 16, wherein a second threshold value for a targeted requested bit rate is determined and wherein the step of determining the requested bit rate consists in selecting the largest bit rate among the supported bit rates which is lower than or equal to the second threshold value minus a provision.
 21. The method according to claim 18, wherein, the requested first part have a first size, said first size is proportional to a size of the chunk identified by the time index i and the determined requested bit rate and a ratio between the determined first available bit rate and the sum.
 22. The method according to claim 16, wherein the four steps are carried out each time a chunk is completely received by the client device.
 23. The method according to claim 16, wherein it involves a further step carried out before step for determining whether the first and at least second available bit rates determined over the paths are larger than a first threshold value (BRTH1), wherein the four steps are carried out exclusively for paths over which the client device determines the determined available bit rate is greater than the first threshold value.
 24. The method according to claim 16, wherein the step of determining said first and second available bit rates consists in computing a round trip time of a request sent by the client device through said first and at least second path and of an acknowledgment message sent in response to said request through said at least first and second path.
 25. The method according to claim 24, wherein it comprises a further step of receiving by the client device a list of the supported bit rates via at least one of the paths and further steps of for receiving for each supported bit rates sizes of the chunks.
 26. The method according to claim 17, said client device further comprising a third communication interface having a communication address, said content being accessible to the client device via a third server communication interface having a communication address, a third path being identified by the communication address of said third communication interface and by the address of the third server communication interface, the requested bit rate being determined form said first, said second and a third available bit rate determining respectively on said first, second and third path, the client device having requested a first part of the chunk identified by the time index i and the requested bit rate via the first path, a second part of said chunk via the second path, a third part of said chunk via the third path, said content being simultaneously accessible by said client device though said first, second and third path, wherein it involves, at said client device further step of: a. When the requested first and second part are completely received by said client device, a first fragment of the third part being received by the client device, a second fragment of the third part being complementary to said first fragment, and when the client device has determined that the available bit rate over the path is less than a third threshold value, sending a request via the path for receiving a first complementary part of said second fragment and sending a request via the path for receiving a second complementary part of the said second fragment, said first and second complementary part having no overlap and aggregation of both said first and second complementary part resulting in the whole second fragment.
 27. A client device for receiving a content to be rendered, said client device comprising at least a first and a second communication interface, wherein said at least first and second communication interface having a communication address, said content being accessible to the client device via at least a first and a second server communication interface having a communication address, a first path being identified by the communication address of said first communication interface and the address of the first server communication interface, at least a second path being identified by the communication address of said second communication interface and the address of the second server communication interface, said content being available under at least two versions having an encoding quality corresponding to a supported bit rate constraint, each of said at least two versions being temporally split into chunks corresponding to an identical duration of the content, a chunk being identified by a time index i and by the supported bit rate, said content being simultaneously accessible by said client device though said at least first and a second path, and wherein said client device comprises: a. Means for determining a first available bit rate on the first path and at least a second available bit rate on the at least second path; b. Means for determining a requested bit rate among the supported bit rate from the determined first available bit rate and the at least determined second available bit rate; c. Means for sending a first request via the first path for receiving a first part of the chunk identified by the time index i and the determined requested bit rate and at least a second request via the at least second path for receiving a second part of said chunk, said parts of the chunk being complementary, each of said parts of the chunk having a size being computed from the determined available bit rate; d. Means for receiving the requested first part via the first path and the at least requested second part via the at least second path.
 28. The client device according to claim 27, wherein it further comprises means for receiving, via at least one of the first and second path, information related to the supported bit rates and for each supported bit rates information related to the size of the chunks
 29. The client device according to claim 28, wherein the means for determining a requested bit rate is adapted for evaluating a sum of the determined first available bit rate and of the determined second available bit rate and said means is adapted for selecting the largest bit rate among the supported bit rates which is lower than or equal to the sum of the determined first available bit rate and of the determined second available bit rate minus a provision.
 30. Client device according to claim 27, wherein it further comprises means for determining whether determined available bit rates exceeds a first threshold and wherein said means for sending request is adapted for sending the request for receiving parts of the chunks exclusively for paths over which the client device determines the determined available bit rate is greater than the first threshold value. 